| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.3.5.4.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.4 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_3_5_4_Manage_Reminders |
| Title | PH.3.5.4 Manage Reminders (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Present the PHR Account Holder with reminders either sent by external sources or internally generated from information in the PHR-S. |
| Purpose | The PHR Account Holder will want to manage reminders sent by external sources (such as the PHR Account Holder’s provider(s)) or generated from information in the PHR (such as guideline-based reminders, prescription refills, or appointment reminders). A reminder is a notification of an upcoming event or activity that usually requires an action by the PHR Account Holder. Reminders may be displayed on a view in the PHR (such as the summary dashboard) and may also be displayed by other electronic means (such sent to an e-mail account). Example(s): The system SHOULD send a reminder of an upcoming appointment as a text message to the PHR Account Holder’s cellular telephone. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Present the PHR Account Holder with reminders either sent by external sources or internally generated from information in the PHR-S.
The PHR Account Holder will want to manage reminders sent by external sources (such as the PHR Account Holder’s provider(s)) or generated from information in the PHR (such as guideline-based reminders, prescription refills, or appointment reminders). A reminder is a notification of an upcoming event or activity that usually requires an action by the PHR Account Holder. Reminders may be displayed on a view in the PHR (such as the summary dashboard) and may also be displayed by other electronic means (such sent to an e-mail account).
Example(s): The system SHOULD send a reminder of an upcoming appointment as a text message to the PHR Account Holder’s cellular telephone.
| PH.3.5.4#01 | SHALL |
The system SHALL present the PHR Account Holder with reminders of scheduled events. |
| PH.3.5.4#02 | SHALL |
The system SHALL manage timely reminders from PHR Account Holder provider(s) to include notifications for services, tests or actions that are due or overdue. |
| PH.3.5.4#03 | SHOULD |
The system SHOULD provide the ability to capture a history of notifications. |
| PH.3.5.4#04 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s response(s) to notifications and/or reminders. |
| PH.3.5.4#05 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding a notification and/or reminder. |
| PH.3.5.4#06 | MAY |
The system MAY provide the ability to transmit to the sender of a notification and/or reminder the PHR Account Holder's response to that notification and/or reminder. |
| PH.3.5.4#07 | SHOULD |
The system SHOULD provide the ability to track PHR Account Holder-configured notifications and/or reminders. |
| PH.3.5.4#08 | SHOULD |
The system SHOULD provide the ability to manage PHR Account Holder notifications and/or reminders based on configuration options (e.g., repetitions or timing of the activity). |
| PH.3.5.4#09 | MAY |
The system MAY provide the ability to present options for the PHR Account Holder to configure preferences for notifications and/or reminders (e.g., posting on the PHR summary screen, e-mail, or text messages to another e-mail account or device). |
| PH.3.5.4#10 | SHOULD |
The system SHOULD provide the ability to update the content of notifications, guidelines, reminders, and associated reference materials. |
| PH.3.5.4#11 | SHOULD |
The system SHOULD provide the ability to receive and update content of notifications, guidelines, reminders, and associated reference materials from the PHR Account Holder’s provider(s). |
| PH.3.5.4#12 | MAY |
The system MAY provide the ability to manage the lifecycle of the states of the notifications and/or reminders. |
| PH.3.5.4#13 | SHOULD |
The system SHOULD provide the ability to update the established criteria that trigger the reminders. |
| PH.3.5.4#14 | conditional SHALL |
IF indications for specific preventive services and accompanying reminders were previously captured, THEN the system SHALL present reminders to the PHR Account Holder of all specific preventive services (e.g., a follow up examination that is scheduled in the coming week). |
| PH.3.5.4#15 | SHOULD |
The system SHOULD provide the ability to receive secure messages of reminders or notifications from the PHR Account Holder's provider(s) to remind the PHR Account Holder of tests or actions that are due or overdue. |
| PH.3.5.4#16 | SHOULD |
The system SHOULD provide the ability to update a repetitive reminder by dismissing the reminder. |
| PH.3.5.4#17 | SHOULD |
The system SHOULD provide the ability to transmit a notification to the PHR Account Holder or the PHR Account Holder's designated representative that a reminder was not acknowledged. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.3.5.4",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Present the PHR Account Holder with reminders either sent by external sources or internally generated from information in the PHR-S.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The PHR Account Holder will want to manage reminders sent by external sources (such as the PHR Account Holder’s provider(s)) or generated from information in the PHR (such as guideline-based reminders, prescription refills, or appointment reminders). A reminder is a notification of an upcoming event or activity that usually requires an action by the PHR Account Holder. Reminders may be displayed on a view in the PHR (such as the summary dashboard) and may also be displayed by other electronic means (such sent to an e-mail account).</p>\n<p>Example(s): The system SHOULD send a reminder of an upcoming appointment as a text message to the PHR Account Holder’s cellular telephone.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL present the PHR Account Holder with reminders of scheduled events.</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://www.hl7.org/fhir/communication.html\">https://www.hl7.org/fhir/communication.html</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL manage timely reminders from PHR Account Holder provider(s) to include notifications for services, tests or actions that are due or overdue.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture a history of notifications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the PHR Account Holder’s response(s) to notifications and/or reminders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding a notification and/or reminder.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to transmit to the sender of a notification and/or reminder the PHR Account Holder's response to that notification and/or reminder.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to track PHR Account Holder-configured notifications and/or reminders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage PHR Account Holder notifications and/or reminders based on configuration options (e.g., repetitions or timing of the activity).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to present options for the PHR Account Holder to configure preferences for notifications and/or reminders (e.g., posting on the PHR summary screen, e-mail, or text messages to another e-mail account or device).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update the content of notifications, guidelines, reminders, and associated reference materials.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive and update content of notifications, guidelines, reminders, and associated reference materials from the PHR Account Holder’s provider(s).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the lifecycle of the states of the notifications and/or reminders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update the established criteria that trigger the reminders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF indications for specific preventive services and accompanying reminders were previously captured, THEN the system SHALL present reminders to the PHR Account Holder of all specific preventive services (e.g., a follow up examination that is scheduled in the coming week).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive secure messages of reminders or notifications from the PHR Account Holder's provider(s) to remind the PHR Account Holder of tests or actions that are due or overdue.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#16</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update a repetitive reminder by dismissing the reminder.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.4#17</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to transmit a notification to the PHR Account Holder or the PHR Account Holder's designated representative that a reminder was not acknowledged.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.4",
"version" : "2.0.1-ballot",
"name" : "PH_3_5_4_Manage_Reminders",
"title" : "PH.3.5.4 Manage Reminders (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Present the PHR Account Holder with reminders either sent by external sources or internally generated from information in the PHR-S.",
"purpose" : "The PHR Account Holder will want to manage reminders sent by external sources (such as the PHR Account Holder’s provider(s)) or generated from information in the PHR (such as guideline-based reminders, prescription refills, or appointment reminders). A reminder is a notification of an upcoming event or activity that usually requires an action by the PHR Account Holder. Reminders may be displayed on a view in the PHR (such as the summary dashboard) and may also be displayed by other electronic means (such sent to an e-mail account).\r\n\r\nExample(s): The system SHOULD send a reminder of an upcoming appointment as a text message to the PHR Account Holder’s cellular telephone.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-01",
"label" : "PH.3.5.4#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL present the PHR Account Holder with reminders of scheduled events.",
"satisfiedBy" : [
"https://www.hl7.org/fhir/communication.html"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-02",
"label" : "PH.3.5.4#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL manage timely reminders from PHR Account Holder provider(s) to include notifications for services, tests or actions that are due or overdue."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-03",
"label" : "PH.3.5.4#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture a history of notifications."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-04",
"label" : "PH.3.5.4#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the PHR Account Holder’s response(s) to notifications and/or reminders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-05",
"label" : "PH.3.5.4#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding a notification and/or reminder."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-06",
"label" : "PH.3.5.4#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to transmit to the sender of a notification and/or reminder the PHR Account Holder's response to that notification and/or reminder."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-07",
"label" : "PH.3.5.4#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to track PHR Account Holder-configured notifications and/or reminders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-08",
"label" : "PH.3.5.4#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage PHR Account Holder notifications and/or reminders based on configuration options (e.g., repetitions or timing of the activity)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-09",
"label" : "PH.3.5.4#09",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to present options for the PHR Account Holder to configure preferences for notifications and/or reminders (e.g., posting on the PHR summary screen, e-mail, or text messages to another e-mail account or device)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-10",
"label" : "PH.3.5.4#10",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update the content of notifications, guidelines, reminders, and associated reference materials."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-11",
"label" : "PH.3.5.4#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive and update content of notifications, guidelines, reminders, and associated reference materials from the PHR Account Holder’s provider(s)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-12",
"label" : "PH.3.5.4#12",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the lifecycle of the states of the notifications and/or reminders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-13",
"label" : "PH.3.5.4#13",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update the established criteria that trigger the reminders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-14",
"label" : "PH.3.5.4#14",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF indications for specific preventive services and accompanying reminders were previously captured, THEN the system SHALL present reminders to the PHR Account Holder of all specific preventive services (e.g., a follow up examination that is scheduled in the coming week)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-15",
"label" : "PH.3.5.4#15",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive secure messages of reminders or notifications from the PHR Account Holder's provider(s) to remind the PHR Account Holder of tests or actions that are due or overdue."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-16",
"label" : "PH.3.5.4#16",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update a repetitive reminder by dismissing the reminder."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.4-17",
"label" : "PH.3.5.4#17",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit a notification to the PHR Account Holder or the PHR Account Holder's designated representative that a reminder was not acknowledged."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.